SKU: 73210204619
moonshine snake plant near me

moonshine snake plant near me Moonshine

Sale price$21.99 Regular price$24.43
Save 10%

Pay in installments of $6.11 with ShopPay, AfterPay and Klarna

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 28 - Aug 2

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

moonshine snake plant near me MoonshineDracaena (Sansevieria) trifasciata 'Moonshine' Dracaena trifasciata 'Moonshine' is a light toned snake plant with broad, upright leaves and a soft grey green surface. The leaves rise from the base in firm, lance shaped fans, with faint horizontal markings and a narrow darker edge. Its colour gives the plant a calm appearance while keeping the strong structure of a snake plant. This cultivar has light grey green foliage on firm vertical leaves. The

Dracaena (Sansevieria) trifasciata 'Moonshine'

Dracaena trifasciata 'Moonshine' is a light-toned snake plant with broad, upright leaves and a soft grey-green surface. The leaves rise from the base in firm, lance-shaped fans, with faint horizontal markings and a narrow darker edge. Its colour gives the plant a calm appearance while keeping the strong structure of a snake plant.

This cultivar has light grey-green foliage on firm vertical leaves. The smooth surface catches light in simple pots, while growth comes from a rhizome below the substrate. New leaves appear from the base and slowly increase the density of the clump.

Light leaves with a fine green edge

  • Leaf colour: Light grey-green blades give the plant a cool, bright look.
  • Leaf edge: A fine dark green margin outlines the leaves and sharpens the light-toned foliage.
  • Growth base: New leaves rise from the rhizome and slowly fill the pot.
  • Indoor shape: Upright, lance-shaped leaves give height from a compact base.
  • Flowering: Mature plants may occasionally produce pale, fragrant flower spikes in settled indoor conditions.

How Moonshine grows in a pot

Dracaena trifasciata is native from southern Nigeria to western Central Tropical Africa and Tanzania, where it grows in seasonally dry tropical conditions. Its firm leaves store water, while the rhizome needs a clear drying phase between waterings. Air around the rhizome is especially important after watering in cooler indoor conditions.

'Moonshine' keeps the firm sword-leaf form of the species, while the light foliage makes dust, splash marks and handling damage easier to notice. New leaves may emerge very light and then settle into a cooler grey-green tone as they mature. In bright indirect light, the leaves usually stay firm and evenly coloured.

The plant usually grows slowly indoors. A snug, stable pot is appropriate because the rhizome does not need a large volume of damp mix around it. When several new shoots have filled the pot or the container begins to deform, move it into a slightly larger pot with fresh, open substrate.

Care for light grey-green foliage

  • Light: In bright indirect light, leaves stay firm and the grey-green colour remains clear. In dimmer rooms, growth slows and the pot dries more gradually.
  • Watering: Water after the mix has dried deeply. Soak evenly, drain fully and let the lower pot dry again before repeating.
  • Substrate: A free-draining mix with pumice, lava rock, coarse sand or fine bark keeps the rhizome aerated after watering.
  • Pot choice: Choose a pot with drainage holes and enough weight to balance the leaves. Empty decorative cover pots after watering.
  • Temperature: Keep it in steady indoor warmth, ideally around 18–27 °C. The root zone should stay warm after watering.
  • Humidity: Average household humidity is enough. Normal room air is adequate for this cultivar.
  • Feeding: Feed lightly during active growth with a diluted balanced or cactus fertiliser. Slow rhizome-based growth needs modest nutrition.
  • Repotting: Repot when the plant has filled the container or the substrate has lost structure. Increase pot size carefully so the new mix dries predictably.
  • Propagation: Divide rooted clumps to keep the light cultivar look consistent. Leaf cuttings can root and may produce growth that does not match the parent plant.

Marks and stress on light leaves

  • Soft bases: Inspect the substrate line, rhizome area and cover pot. Soft tissue near the base usually means the lower plant stayed wet too long.
  • Wrinkled leaves: Check the root system as well as dryness. Root damage can make leaves wrinkle even when the pot has been watered.
  • Brown tips or edges: Review watering consistency, mineral buildup, old knocks and temperature dips. Trim only dry tissue if needed.
  • Marked foliage: Wipe leaves gently with a soft damp cloth. The light surface shows dust and water spots quickly.
  • Weak new growth: Move the plant closer to bright filtered light and check that the pot size matches the root system.

Placement around pets

Keep Dracaena trifasciata 'Moonshine' away from pets and small children who may chew the leaves. Snake plants contain saponins, which can cause nausea, vomiting or diarrhoea in cats and dogs if ingested. A raised, stable position also helps keep the light leaves free from knocks and bite marks.

The name behind Dracaena trifasciata

The accepted botanical name for the species is Dracaena trifasciata, while Sansevieria trifasciata remains the older name still widely used in houseplant retail and care information. The genus name Dracaena comes from the Greek drakaina, meaning “female dragon”, historically linked to red resin in some dragon tree relatives. The species epithet trifasciata means “three-banded” or “marked with three bands”, referring to the banded foliage pattern associated with the species.

Dracaena trifasciata 'Moonshine' has soft grey-green leaves, faint markings and slow basal growth in an upright clump.

Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 73210204619

Discover Niche Categories That Outsell moonshine snake plant near me

Top-Converting Item to Boost Your Average Order

4.1 ★★★★★
Based on 13 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
A
Amazon Customer
Houston, US
★★★★★ 5
This is a "Go-To" for thinking about Cloud Challenges.
Format: Paperback
Delivering and managing fully realized applications in the cloud is different. Different approaches to classic engineering problems than traditional On Premise development and different ways of thinking through the problems of "always available" solutions. I've been in the software delivery business a long time, and with the cloud emerging, for good and ill: I understand the problems, but may be just a little set in my ways. I find this book helps me re-frame challenges in a way that aligns with the strengths of cloud computing. Solve the same problems faster, by thinking about them differently. I'm finding "97 Things Every Cloud Engineer Should Know" great for re-centering my expectations about Cloud Native development and deployment of assets. I started reading it cover to cover over the Christmas Holiday but now i just pick it up and look for the group of essays about exactly the problem I'm wrestling with. P.S. I'm heartened by the editors commitment to Black Lives Matter and Rule of Law. Mentioned only to balance the concerns from another review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on January 24, 2021
C
Verified Purchase
cloud-learner
Bozeman, US
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
E
Verified Purchase
Engineer Dude
Lexington, US
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
P
Verified Purchase
PeaceBee
Cuba, US
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
N
Nilendu Misra
Cuba, US
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend. I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this. Let's summarize some key insights - -- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud. -- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services. -- Distinguish between "availability" and "uptime" and measure each separately, and concretely. -- In FaaS/Serverless, calling a function synchronously increases debugging complexity. -- Good code is like good joke - it needs no explanation. -- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains. -- Cloud is not optimized for replacing static infrastructures. -- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra. -- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less. -- Adopt an "assume breach" stance for everything. Have a break-glass account. -- Ensure you have a thorough understanding of where and how secrets are secured. -- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop. -- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure. -- Resilience is something you "do", not something you "have". Resilience is a verb. -- Moving from one class of nines to the next is 10 times more expensive. -- Production System really means "system that someone else, anyone else, can hold you accountable for". -- Most common theme across incidents is that something, somewhere was surprising. -- Incidents are unplanned investments...your challenge is to maximize ROI. -- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases). -- Architecture diagram is also a map of failure modes. -- Async communication is a friend of Cloud Reliability. -- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env. -- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign. -- It is hard to write good tests for bad code. -- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023

recommand products